Check Point Exposure Management Alerts for Microsoft Sentinel

Solution: Check Point Cyberint Alerts

Check Point Cyberint Alerts Logo

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Solutions Index


Attribute Value
Publisher Check Point
Support Tier Partner
Support Link https://www.checkpoint.com/support-services/contact-support/
Categories Security - Threat Intelligence
Version 3.2.0
Author Check Point - support@checkpoint.com
First Published 2025-03-18
Last Updated 2026-09-24
Solution Folder Check Point Cyberint Alerts
Marketplace Azure Marketplace · Popularity: 🔵 Medium (63%)

Check Point provides Microsoft Sentinel integration to streamline critical Alerts and bring enriched threat intelligence from the Infinity External Risk Management solution into Microsoft Sentinel. This simplifies the process of tracking the status of tickets with automatic sync updates across systems. Using this new integration for Microsoft Sentinel, existing Check Point Exposure Management and Microsoft Sentinel customers can easily pull logs based on Check Point Exposure Management findings into Microsoft Sentinel platform.

NOTE: Microsoft recommends installation of Check Point Exposure Management Alerts Connector (via Codeless Connector Platform). This connector is build on the Codeless Connector Platform (CCP), which uses the Log Ingestion API, which replaces ingestion via the deprecated HTTP Data Collector API. CCP-based data connectors also support Data Collection Rules (DCRs) offering transformations and enrichment.

Contents

Data Connectors

This solution provides 1 data connector(s):

Tables Used

This solution uses 1 table(s):

Table Used By Connectors Used By Content
argsentdc_CL Check Point Cyberint Alerts Connector (via Codeless Connector Platform) Analytics, Workbooks

Content Items

This solution includes 12 content item(s):

Content Type Count
Playbooks 8
Analytic Rules 2
Workbooks 1
Parsers 1

Analytic Rules

Name Severity Tactics Tables Used
Check Point Exposure Management - Alert Ingestion Anomaly Medium DefenseEvasion argsentdc_CL
Check Point Exposure Management - Argos alerts to incidents Medium InitialAccess, DefenseEvasion argsentdc_CL

Workbooks

Name Tables Used
CPEMAlertOverview argsentdc_CL

Playbooks

Name Description Tables Used
Check Point Exposure Management - Credential Leak Validation and Response When a new Microsoft Sentinel incident is created for leaked credentials, this playbook queries the ... -
Check Point Exposure Management - Exporter (Microsoft Sentinel → Argos) When a Microsoft Sentinel incident status changes, this playbook pushes the new status to the corres... -
Check Point Exposure Management - Fetch Attachments On-Demand On-demand playbook that fetches alert attachments and analysis report for a Microsoft Sentinel incid... -
Check Point Exposure Management - IOC Enrichment and Triage When a new Microsoft Sentinel incident is created, this playbook enriches IOC entities (IPs, domains... -
Check Point Exposure Management - Inbound Status Sync (Argos → Microsoft Sentinel) Runs on a schedule and mirrors Argos alert status changes onto the Microsoft Sentinel incidents crea... -
Check Point Exposure Management - Manual Status Update (Microsoft Sentinel → Argos) On-demand playbook that reads the current Microsoft Sentinel incident status and pushes it to the co... -
Check Point Exposure Management - Phishing Takedown When a new Microsoft Sentinel incident is created for a phishing website alert, this playbook extrac... -
Check Point Exposure Management - Vulnerability Exploitation Monitoring When a new Microsoft Sentinel incident is created containing CVE identifiers, this playbook enriches... -

Parsers

Name Description Tables Used
CPEMAlerts - AADNonInteractiveUserSignInLogs (read)
SigninLogs (read)
TacitRed_Findings_CL (read)
Internal use:
BehaviorAnalytics (read)

Additional Documentation

📄 Source: Check Point Cyberint Alerts/README.md

Overview

This solution integrates Check Point Exposure Management with Microsoft Sentinel and keeps alert status in sync in both directions. Argos alerts become Microsoft Sentinel incidents, status changes made in either system are mirrored to the other, and SOC teams can enrich and respond to alerts from Microsoft Sentinel.

What's Included

Component Description
Data Connector (CCP) Polls the Argos Alerts API every 5 minutes for alerts created or changed in that window
2 Analytic Rules Creates an incident per Argos alert; detects ingestion gaps
9 Playbook templates Status sync in both directions, enrichment, response, and the automation rule that wires outbound sync
1 Parser CPEMAlerts: latest state of each alert with category metadata
1 Workbook Alert overview, status distribution, and sync health monitoring

Architecture

            ┌──────────────────────────────────────┐
            │  Check Point Exposure Management     │
            │  (Argos Alerts API)                  │
            └───────┬──────────────────────▲───────┘
                    │ POST /alerts          │ GET /alerts/{ref_id}
                    │ (update_date window)  │ PUT /alerts/status
                    ▼                       │
          ┌───────────────────┐   ┌─────────┴──────────┐
          │ CCP data connector│   │ Exporter           │
          └─────────┬─────────┘   │ (Sentinel → Argos) │
                    ▼             └─────────▲──────────┘
          ┌───────────────────┐             │ Automation rule:
          │ argsentdc_CL      │             │ status changed
          │ one row per change│             │
          └──┬─────────────┬──┘   ┌─────────┴──────────┐
             │             │      │ Microsoft Sentinel │
   first seen│             │later │ incidents          │
             ▼             ▼      └──▲──────────────▲──┘
  ┌────────────────┐ ┌──────────────┴────┐          │
  │ Analytic rule  │ │ InboundStatusSync │          │
  │ Argos alerts   │ │ (Argos → Sentinel)│          │
  │ to incidents   ├─┼───────────────────┼──────────┘
  └────────────────┘ └───────────────────┘  creates incident + alert
                                            with ref_id Custom Detail

How the sync works:

[Content truncated...]

Release Notes

Version Date Modified (DD-MM-YYYY) Change History
3.2.0 18-09-2026 • Two-way status sync between Argos and Microsoft Sentinel; the newest change wins. New Check_Point_EM_InboundStatusSync playbook, and Check_Point_EM_AutomationRules is now part of the package.
• New analytic rule, Argos alerts to incidents, replaces the Check_Point_EM_Importer playbook, which could not ingest because the Logs Ingestion API does not support the SecurityAlert table.
• Data connector polls on update_date and requests 100 alerts per page.
• Fixed Argos calls failing with HTTP 401, the status update endpoint, ref_id extraction, and the status and closure reason mapping.
• Upgrading from 3.1.x requires reconnecting the data connector and recreating the sync playbooks; see the solution README.
3.1.4 08-09-2026 Fixed Check_Point_EM_Importer playbook creation failing with InvalidTemplate: Unable to parse language expression '': expected token 'Identifier' and actual 'EndOfData'. The empty Entities JSON array literal in the SecurityAlert ingestion body was interpreted by ARM as an empty template expression; it is now emitted via string(createArray()) in both the solution package and the standalone playbook template.
3.1.3 21-08-2026 Fixed ARM template expression escaping in nested content templates (stray ] in dcrConfig and playbook expressions) that caused data connector Connect deployment to fail with a template language expression parse error.
Fixed alerts polling request body to send strict JSON (double-quoted): the Argos API now rejects single-quoted bodies with 422 Unprocessable Entity.
Fixed connection template parameter defaults: placeholder values (e.g. "severity") leaked into the API request body when optional connector fields were left empty, failing the connectivity check with 422 (invalid severity enum). Optional filters now default to empty and are omitted from the request.
3.1.2 02-06-2026 Updated support contact information and documentation links.
3.1.0 10-03-2026 Update Data Connector, add bi-directional sync playbooks, analytic rule (ingestion anomaly), workbook (alert overview & sync health), and automation rules.
3.0.0 17-06-2025 Initial Solution release.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Solutions Index